Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8d4c382cb2e4590d374e569a8b44ca46083f3537c7a1f725862608766afdfa19

Tx prefix hash: b5308dce4942c5d1025bdadd73ecea9f94b64b267688e438a478f994abd8e727
Tx public key: c663861517af31a8f0b45b66d544194ef346b7c0c45c8aedc9de09b831446c82
Timestamp: 1698640579 Timestamp [UCT]: 2023-10-30 04:36:19 Age [y:d:h:m:s]: 01:177:12:26:19
Block: 880690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387877 RingCT/type: yes/0
Extra: 01c663861517af31a8f0b45b66d544194ef346b7c0c45c8aedc9de09b831446c8202110000000233af99f4000000000000000000

1 output(s) for total of 0.741153988000 dcy

stealth address amount amount idx
00: f10a1e2c5817aa2849002bfce332cf17d5d2fc3430af91453c91dd3b4223dafa 0.741153988000 1336256 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 880700, "vin": [ { "gen": { "height": 880690 } } ], "vout": [ { "amount": 741153988, "target": { "key": "f10a1e2c5817aa2849002bfce332cf17d5d2fc3430af91453c91dd3b4223dafa" } } ], "extra": [ 1, 198, 99, 134, 21, 23, 175, 49, 168, 240, 180, 91, 102, 213, 68, 25, 78, 243, 70, 183, 192, 196, 92, 138, 237, 201, 222, 9, 184, 49, 68, 108, 130, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8