Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6046d534540277fcd1d5bef7926fc9147d150e8d59aa2939272d4cea5dc61d

Tx prefix hash: e70102f35371540b75cc623262eb6cc32d64f4fb22b7d38ab8cf35792bf7fcce
Tx public key: ac5d33b6735d70dec3d055ea33858e4a08fee558df7902e7e0f14c01a05112f8
Timestamp: 1724022899 Timestamp [UCT]: 2024-08-18 23:14:59 Age [y:d:h:m:s]: 00:261:18:25:08
Block: 1090914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186965 RingCT/type: yes/0
Extra: 01ac5d33b6735d70dec3d055ea33858e4a08fee558df7902e7e0f14c01a05112f802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b4a58e127ca532b1b1e0f4846e5068c804a239c2b4e40ca1520f931074c03cd 0.600000000000 1565539 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": 1090924, "vin": [ { "gen": { "height": 1090914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b4a58e127ca532b1b1e0f4846e5068c804a239c2b4e40ca1520f931074c03cd" } } ], "extra": [ 1, 172, 93, 51, 182, 115, 93, 112, 222, 195, 208, 85, 234, 51, 133, 142, 74, 8, 254, 229, 88, 223, 121, 2, 231, 224, 241, 76, 1, 160, 81, 18, 248, 2, 17, 0, 0, 0, 6, 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