Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118e5d04aa2f462b5acd609fc3e37202d67cfc521dbd03ee8441ce4264df4748

Tx prefix hash: e5cd23badd403fe4fc913c123d1a05f15e770b8bf74a91cb4c9c4e570ad171a7
Tx public key: 45fc8c44ed8c261677eac1fc2a0dedc68942ecae21e74d55ae35ab1f58291a0e
Timestamp: 1720876539 Timestamp [UCT]: 2024-07-13 13:15:39 Age [y:d:h:m:s]: 00:270:05:17:57
Block: 1064835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193043 RingCT/type: yes/0
Extra: 0145fc8c44ed8c261677eac1fc2a0dedc68942ecae21e74d55ae35ab1f58291a0e02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19c160bff910458d47d115d9a94eb256a6097c7fcc30300b0c1f210c6e20c8a3 0.600000000000 1535374 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": 1064845, "vin": [ { "gen": { "height": 1064835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c160bff910458d47d115d9a94eb256a6097c7fcc30300b0c1f210c6e20c8a3" } } ], "extra": [ 1, 69, 252, 140, 68, 237, 140, 38, 22, 119, 234, 193, 252, 42, 13, 237, 198, 137, 66, 236, 174, 33, 231, 77, 85, 174, 53, 171, 31, 88, 41, 26, 14, 2, 17, 0, 0, 0, 10, 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