Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a825c0d7870c4b682d893a19beb738a88fee0d282ded42a6b27a58e03557f6ae

Tx prefix hash: a41a17089a3ac0635d7cee0c036e5945623b82d7516d812cb84ef43e74901c60
Tx public key: 548d4f7a16963fe48a6af8b12446aca1a27aa2430407a5897018ae4912d338f9
Timestamp: 1734853677 Timestamp [UCT]: 2024-12-22 07:47:57 Age [y:d:h:m:s]: 00:110:11:33:06
Block: 1180606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78735 RingCT/type: yes/0
Extra: 01548d4f7a16963fe48a6af8b12446aca1a27aa2430407a5897018ae4912d338f90211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a72e4da629497a319ed51a49a0423fb7d3cf0d2ef1349d1580fdf0ef0bcf2c49 0.600000000000 1667019 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": 1180616, "vin": [ { "gen": { "height": 1180606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a72e4da629497a319ed51a49a0423fb7d3cf0d2ef1349d1580fdf0ef0bcf2c49" } } ], "extra": [ 1, 84, 141, 79, 122, 22, 150, 63, 228, 138, 106, 248, 177, 36, 70, 172, 161, 162, 122, 162, 67, 4, 7, 165, 137, 112, 24, 174, 73, 18, 211, 56, 249, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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