Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d303cea279c4c4442e29d2668c419ee9173fb2ffd2d68cc2776bd74b68cb0bd7

Tx prefix hash: 2dec5b18d2f1cb1b1e3379ed335752ef44a3c7776cf2b09474357dba48482dae
Tx public key: c758f0370d68e937bf7874e54294cbbbba90d8b799dcb2406ec769e7d856943f
Timestamp: 1693362027 Timestamp [UCT]: 2023-08-30 02:20:27 Age [y:d:h:m:s]: 01:281:15:36:01
Block: 836895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462464 RingCT/type: yes/0
Extra: 01c758f0370d68e937bf7874e54294cbbbba90d8b799dcb2406ec769e7d856943f021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.035188716000 dcy

stealth address amount amount idx
00: e4ab10664237469ffb5a1b5cb04ded40252d783c4f40fc6cc5bdcf4e15bd4c8b 1.035188716000 1289501 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": 836905, "vin": [ { "gen": { "height": 836895 } } ], "vout": [ { "amount": 1035188716, "target": { "key": "e4ab10664237469ffb5a1b5cb04ded40252d783c4f40fc6cc5bdcf4e15bd4c8b" } } ], "extra": [ 1, 199, 88, 240, 55, 13, 104, 233, 55, 191, 120, 116, 229, 66, 148, 203, 187, 186, 144, 216, 183, 153, 220, 178, 64, 110, 199, 105, 231, 216, 86, 148, 63, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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