Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899196c170cef15fc82ec31a5211278151bd8c25e588d8dc30ad1acec9b6a0de

Tx prefix hash: 214b375de90f6f25d84447862b62e5c403c332ec24df2a815aa822e1ad1e6727
Tx public key: 20d9f99592fad5e9fd4e8deb63fa9e69b40ca071fb3c6c668ddd02fe243cedd2
Timestamp: 1721834086 Timestamp [UCT]: 2024-07-24 15:14:46 Age [y:d:h:m:s]: 00:090:13:10:55
Block: 1072759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64832 RingCT/type: yes/0
Extra: 0120d9f99592fad5e9fd4e8deb63fa9e69b40ca071fb3c6c668ddd02fe243cedd2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1e04a36ad33c57317d5bef0532824fbf44df3cba2d025bdac4424814681db39 0.600000000000 1545254 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": 1072769, "vin": [ { "gen": { "height": 1072759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1e04a36ad33c57317d5bef0532824fbf44df3cba2d025bdac4424814681db39" } } ], "extra": [ 1, 32, 217, 249, 149, 146, 250, 213, 233, 253, 78, 141, 235, 99, 250, 158, 105, 180, 12, 160, 113, 251, 60, 108, 102, 141, 221, 2, 254, 36, 60, 237, 210, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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