Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0ca005c116473fb4de41627a11c73796dd83fa4b60d97f62358c1c90b038f1

Tx prefix hash: 9132bbafe628610f2125c378cb9b70f3fa94fe0e1e20fcbf7ce3f29040c4f23c
Tx public key: b3cd0a80c226381b851fea57e09c4cb610baeb678728b52fec58ac8b57c84385
Timestamp: 1732744150 Timestamp [UCT]: 2024-11-27 21:49:10 Age [y:d:h:m:s]: 00:178:02:11:11
Block: 1163109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127136 RingCT/type: yes/0
Extra: 01b3cd0a80c226381b851fea57e09c4cb610baeb678728b52fec58ac8b57c843850211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae493a0fba4200a7a8c9dc5678bd80c3e86c89bc33e71d093173f8b531acacf 0.600000000000 1648774 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": 1163119, "vin": [ { "gen": { "height": 1163109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae493a0fba4200a7a8c9dc5678bd80c3e86c89bc33e71d093173f8b531acacf" } } ], "extra": [ 1, 179, 205, 10, 128, 194, 38, 56, 27, 133, 31, 234, 87, 224, 156, 76, 182, 16, 186, 235, 103, 135, 40, 181, 47, 236, 88, 172, 139, 87, 200, 67, 133, 2, 17, 0, 0, 0, 5, 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