Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b574ca94a1de50f3e913461c8326e7d83941a59162fd9c535ba195eb045297b6

Tx prefix hash: 47773b0d0b3748036c1a2456294f7870de1a073aa6c173fe8a886e3e397462d6
Tx public key: e7a414a8aed4338e51f7e81aab7be976f0d3a6e7d39bcafca24bd80a130c5c9b
Timestamp: 1715028609 Timestamp [UCT]: 2024-05-06 20:50:09 Age [y:d:h:m:s]: 00:356:18:23:45
Block: 1016351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255029 RingCT/type: yes/0
Extra: 01e7a414a8aed4338e51f7e81aab7be976f0d3a6e7d39bcafca24bd80a130c5c9b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7b26cfd67be42feaad3ac17c4270bd7b2c07c67b399d4ff0ce0a76fc23eacf1 0.600000000000 1479906 of 15

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": 1016361, "vin": [ { "gen": { "height": 1016351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7b26cfd67be42feaad3ac17c4270bd7b2c07c67b399d4ff0ce0a76fc23eacf1" } } ], "extra": [ 1, 231, 164, 20, 168, 174, 212, 51, 142, 81, 247, 232, 26, 171, 123, 233, 118, 240, 211, 166, 231, 211, 155, 202, 252, 162, 75, 216, 10, 19, 12, 92, 155, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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