Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5b4daa6eb4cf1d11a785244e2661f498ff85d56bbb87871ca8ed973d5320a8

Tx prefix hash: 160e474d4f3ee2924787196c3db627bf3bec945c49ea14874dace66c6cd0e363
Tx public key: 7fcf5072b71d54a61085e81ca4a41ce3a3e5422828c8dd50e6cbf9c07153a61f
Timestamp: 1720423307 Timestamp [UCT]: 2024-07-08 07:21:47 Age [y:d:h:m:s]: 00:268:21:08:31
Block: 1061073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192090 RingCT/type: yes/0
Extra: 017fcf5072b71d54a61085e81ca4a41ce3a3e5422828c8dd50e6cbf9c07153a61f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c1603e363fba0dfa8bd57effac0780d86ff8f6ae6a1f96e76f293943e16f16 0.600000000000 1531564 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": 1061083, "vin": [ { "gen": { "height": 1061073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c1603e363fba0dfa8bd57effac0780d86ff8f6ae6a1f96e76f293943e16f16" } } ], "extra": [ 1, 127, 207, 80, 114, 183, 29, 84, 166, 16, 133, 232, 28, 164, 164, 28, 227, 163, 229, 66, 40, 40, 200, 221, 80, 230, 203, 249, 192, 113, 83, 166, 31, 2, 17, 0, 0, 0, 5, 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