Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af0ed5e796802476255d6f96d1c71b41712f691bf624cf502d64bfe20981f19b

Tx prefix hash: d9b036770c2981aa43161f2086045a7fc1c936dba0f9e0485062e759c0f847d8
Tx public key: 602ccee72ca0397d37b2cfb933b6b708f6a59e843963005ecfa3fe263e845b80
Timestamp: 1697408855 Timestamp [UCT]: 2023-10-15 22:27:35 Age [y:d:h:m:s]: 02:025:21:29:31
Block: 870469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538122 RingCT/type: yes/0
Extra: 01602ccee72ca0397d37b2cfb933b6b708f6a59e843963005ecfa3fe263e845b80021100000003faf35c9c000000000000000000

1 output(s) for total of 0.801262616000 dcy

stealth address amount amount idx
00: c0542f1c18497674b6f4839740aca77b3eb7fa64e205d07d8576b6c30b299393 0.801262616000 1325348 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": 870479, "vin": [ { "gen": { "height": 870469 } } ], "vout": [ { "amount": 801262616, "target": { "key": "c0542f1c18497674b6f4839740aca77b3eb7fa64e205d07d8576b6c30b299393" } } ], "extra": [ 1, 96, 44, 206, 231, 44, 160, 57, 125, 55, 178, 207, 185, 51, 182, 183, 8, 246, 165, 158, 132, 57, 99, 0, 94, 207, 163, 254, 38, 62, 132, 91, 128, 2, 17, 0, 0, 0, 3, 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