Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36db120bc986f9a6db64a7967de44943a41e24ddd5fcf7f8b938aaf8c9dc6e5

Tx prefix hash: 07f7c377e6d95213fde91f69718739d66f809fa6880352df24663eec8c52e9aa
Tx public key: 7bbb9de9bf635e69ddfef80486d52193a73e44106a04ab8935169908e6a1612b
Timestamp: 1720406217 Timestamp [UCT]: 2024-07-08 02:36:57 Age [y:d:h:m:s]: 00:198:04:06:47
Block: 1060925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141753 RingCT/type: yes/0
Extra: 017bbb9de9bf635e69ddfef80486d52193a73e44106a04ab8935169908e6a1612b02110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36502c4e5047a2343de7d487c511a84c0e703c3b4d9d5754b6e5a394ddbed93f 0.600000000000 1531414 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": 1060935, "vin": [ { "gen": { "height": 1060925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36502c4e5047a2343de7d487c511a84c0e703c3b4d9d5754b6e5a394ddbed93f" } } ], "extra": [ 1, 123, 187, 157, 233, 191, 99, 94, 105, 221, 254, 248, 4, 134, 213, 33, 147, 167, 62, 68, 16, 106, 4, 171, 137, 53, 22, 153, 8, 230, 161, 97, 43, 2, 17, 0, 0, 0, 18, 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