Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99616940e727be29544ddfe09597045d90a8a1509bc16bb4b48bbebf4ec83acd

Tx prefix hash: 73297f2a1305f067a3dc2cf4828d4d035d0605f46af9c477f3f2a4539d40fbd1
Tx public key: 949f2663d988d686a2d1a6888ad4dc3869dd8effc6cd13a1bff111be322e3d66
Timestamp: 1695437298 Timestamp [UCT]: 2023-09-23 02:48:18 Age [y:d:h:m:s]: 01:192:13:42:19
Block: 854114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398697 RingCT/type: yes/0
Extra: 01949f2663d988d686a2d1a6888ad4dc3869dd8effc6cd13a1bff111be322e3d66021100000004faf35c9c000000000000000000

1 output(s) for total of 0.907749062000 dcy

stealth address amount amount idx
00: b67114a7e3e6d70519024c478e6fe4517aea344f29c868e0785e27ce73478d69 0.907749062000 1308068 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": 854124, "vin": [ { "gen": { "height": 854114 } } ], "vout": [ { "amount": 907749062, "target": { "key": "b67114a7e3e6d70519024c478e6fe4517aea344f29c868e0785e27ce73478d69" } } ], "extra": [ 1, 148, 159, 38, 99, 217, 136, 214, 134, 162, 209, 166, 136, 138, 212, 220, 56, 105, 221, 142, 255, 198, 205, 19, 161, 191, 241, 17, 190, 50, 46, 61, 102, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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