Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1b966789ceb0f125226ed1d751d76a7080208e55e8a4b9e04c166a47a33fa7

Tx prefix hash: 4cfb5c246978be28a59120c8dc37bc44e6fea33095c2726c4d79c63c1376f841
Tx public key: 185fb883519874dff0c1d4233bd180547e1808e5a0fe34201c5c9d694383759a
Timestamp: 1720569293 Timestamp [UCT]: 2024-07-09 23:54:53 Age [y:d:h:m:s]: 00:258:20:52:30
Block: 1062283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184930 RingCT/type: yes/0
Extra: 01185fb883519874dff0c1d4233bd180547e1808e5a0fe34201c5c9d694383759a02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6df4e89ca6a4bd9ab49c12deeb8f8037d486eb3fe7db3ab71f29cae25d04283 0.600000000000 1532784 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": 1062293, "vin": [ { "gen": { "height": 1062283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6df4e89ca6a4bd9ab49c12deeb8f8037d486eb3fe7db3ab71f29cae25d04283" } } ], "extra": [ 1, 24, 95, 184, 131, 81, 152, 116, 223, 240, 193, 212, 35, 59, 209, 128, 84, 126, 24, 8, 229, 160, 254, 52, 32, 28, 92, 157, 105, 67, 131, 117, 154, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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