Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3f73974ce85e6e452bd75c19d5d0c896dde8a59f83f2ad819678bd80b405b7

Tx prefix hash: e276064378249a9bf7492625b46e101336bdfd10db3f707d08e6afa48319a30a
Tx public key: 13e37b1e0adfba0b674b37a4dfd0179d3ab11cbf3d3addd74155c28a4747151a
Timestamp: 1740868267 Timestamp [UCT]: 2025-03-01 22:31:07 Age [y:d:h:m:s]: 00:300:00:25:58
Block: 1230097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212233 RingCT/type: yes/0
Extra: 0113e37b1e0adfba0b674b37a4dfd0179d3ab11cbf3d3addd74155c28a4747151a021100000010007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbd4d3db6277fda879ba9132d869ff8df6b6fb65ea101f626759a335d99ab898 0.600000000000 1716992 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": 1230107, "vin": [ { "gen": { "height": 1230097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbd4d3db6277fda879ba9132d869ff8df6b6fb65ea101f626759a335d99ab898" } } ], "extra": [ 1, 19, 227, 123, 30, 10, 223, 186, 11, 103, 75, 55, 164, 223, 208, 23, 157, 58, 177, 28, 191, 61, 58, 221, 215, 65, 85, 194, 138, 71, 71, 21, 26, 2, 17, 0, 0, 0, 16, 0, 127, 151, 138, 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