Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ada6a163567e01b1cd9a1100bfc9c29caaabd4123d194bc4c3f291857b52f2

Tx prefix hash: 34f78138f68c1c021659ebd1b1ab297677b00e4c39f360b07898366522b7e9c4
Tx public key: fb2ad2b7a9059b6431f0313ec75cbdb0218224c0e872d5dc866b9755fd0105e2
Timestamp: 1761258629 Timestamp [UCT]: 2025-10-23 22:30:29 Age [y:d:h:m:s]: 00:060:09:09:19
Block: 1396507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43212 RingCT/type: yes/0
Extra: 01fb2ad2b7a9059b6431f0313ec75cbdb0218224c0e872d5dc866b9755fd0105e2021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf07a150b1a842d424be5ffacba748e2a9d373c775750ba996b20c1343c3fe57 0.600000000000 1884794 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": 1396517, "vin": [ { "gen": { "height": 1396507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf07a150b1a842d424be5ffacba748e2a9d373c775750ba996b20c1343c3fe57" } } ], "extra": [ 1, 251, 42, 210, 183, 169, 5, 155, 100, 49, 240, 49, 62, 199, 92, 189, 176, 33, 130, 36, 192, 232, 114, 213, 220, 134, 107, 151, 85, 253, 1, 5, 226, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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