Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32434bd5165b3f0be09662f500996286d34393528c69bec22a5d3f7085728373

Tx prefix hash: 20a2fa069e6fb726b200faad79c2cd4aa31cb4bf55c4d5c2d19337e34f6f977d
Tx public key: bad481d9b38a19a45d541fd8fcfd0db1157ff2879bd665fc1c2c41b1cc5a79ac
Timestamp: 1588408004 Timestamp [UCT]: 2020-05-02 08:26:44 Age [y:d:h:m:s]: 05:206:09:36:29
Block: 97704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1320855 RingCT/type: yes/0
Extra: 01bad481d9b38a19a45d541fd8fcfd0db1157ff2879bd665fc1c2c41b1cc5a79ac02110000002c4ac5aa02000000000000000000

1 output(s) for total of 291.255647231000 dcy

stealth address amount amount idx
00: bca5b9ac1d40828375b87d5d2ed968b3f30a4b3b4d784d0c7e1f486c4d4e413f 291.255647231000 172931 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": 97714, "vin": [ { "gen": { "height": 97704 } } ], "vout": [ { "amount": 291255647231, "target": { "key": "bca5b9ac1d40828375b87d5d2ed968b3f30a4b3b4d784d0c7e1f486c4d4e413f" } } ], "extra": [ 1, 186, 212, 129, 217, 179, 138, 25, 164, 93, 84, 31, 216, 252, 253, 13, 177, 21, 127, 242, 135, 155, 214, 101, 252, 28, 44, 65, 177, 204, 90, 121, 172, 2, 17, 0, 0, 0, 44, 74, 197, 170, 2, 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