Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b09d41d3915a74721bd58875d66083029e1335cf6a4ad5c3076b0830965dc29b

Tx prefix hash: d37780ae91737d381c968cfa0e065b337bad9e766535698552458c706643edb3
Tx public key: 52bd5194c097037953bc2d0a28f2c9e4e87941416b9d0e15e1b785d3dc5cc18d
Timestamp: 1725148811 Timestamp [UCT]: 2024-09-01 00:00:11 Age [y:d:h:m:s]: 00:217:08:10:58
Block: 1100237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155195 RingCT/type: yes/0
Extra: 0152bd5194c097037953bc2d0a28f2c9e4e87941416b9d0e15e1b785d3dc5cc18d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a06062baa0936a27e6305c7b5d8a276ead48f167644f7f9e8d64f9176cac41f4 0.600000000000 1576212 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": 1100247, "vin": [ { "gen": { "height": 1100237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a06062baa0936a27e6305c7b5d8a276ead48f167644f7f9e8d64f9176cac41f4" } } ], "extra": [ 1, 82, 189, 81, 148, 192, 151, 3, 121, 83, 188, 45, 10, 40, 242, 201, 228, 232, 121, 65, 65, 107, 157, 14, 21, 225, 183, 133, 211, 220, 92, 193, 141, 2, 17, 0, 0, 0, 3, 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