Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4886029d5244364b4ac126723fca513cedd77afac26eef92106d360edf8bd97b

Tx prefix hash: c1f729aeb3205280f267c42895a8d3d00fea82d5ce7407e286fb225872e5aeb9
Tx public key: 57ed85163ec8f4fd5d07a7123cbda9d89e1fa7f03651dc7a07f38061f92fd02f
Timestamp: 1734687650 Timestamp [UCT]: 2024-12-20 09:40:50 Age [y:d:h:m:s]: 00:095:01:51:34
Block: 1179233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67708 RingCT/type: yes/0
Extra: 0157ed85163ec8f4fd5d07a7123cbda9d89e1fa7f03651dc7a07f38061f92fd02f0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64062a1909532c8b41e1b4095c4a604aa260322619d2cd7e56c0225050f1e14 0.600000000000 1665624 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": 1179243, "vin": [ { "gen": { "height": 1179233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64062a1909532c8b41e1b4095c4a604aa260322619d2cd7e56c0225050f1e14" } } ], "extra": [ 1, 87, 237, 133, 22, 62, 200, 244, 253, 93, 7, 167, 18, 60, 189, 169, 216, 158, 31, 167, 240, 54, 81, 220, 122, 7, 243, 128, 97, 249, 47, 208, 47, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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