Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42abf81faea12e18dccabf7ad713a1bd10ab8aadb5773ffd6ea1552b9f1353c6

Tx prefix hash: 930f4df7d3b14b2e4d62cdea1c0a2514e880022b32cc48875b09b70b0cde563c
Tx public key: 3cb76481bbf2691d29b42fa3bfede0d4bd90d8a9432a7665e4df090e1e747447
Timestamp: 1695301344 Timestamp [UCT]: 2023-09-21 13:02:24 Age [y:d:h:m:s]: 01:204:17:17:41
Block: 852981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407392 RingCT/type: yes/0
Extra: 013cb76481bbf2691d29b42fa3bfede0d4bd90d8a9432a7665e4df090e1e74744702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.915629782000 dcy

stealth address amount amount idx
00: a112754bfe7d4cc164d8c7d3b772f63b7e22e62c0dd65419de968cc2e75f2fc6 0.915629782000 1306853 of 0

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": 852991, "vin": [ { "gen": { "height": 852981 } } ], "vout": [ { "amount": 915629782, "target": { "key": "a112754bfe7d4cc164d8c7d3b772f63b7e22e62c0dd65419de968cc2e75f2fc6" } } ], "extra": [ 1, 60, 183, 100, 129, 187, 242, 105, 29, 41, 180, 47, 163, 191, 237, 224, 212, 189, 144, 216, 169, 67, 42, 118, 101, 228, 223, 9, 14, 30, 116, 116, 71, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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