Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3498c3191d4ef4984be19b43077d63f9f6f8695b6895c824bd4ac09662d2735

Tx prefix hash: f5baaef6f7398fac83d34a46048cf75d01dbb2b8bf08605ca5b3084df9dfa660
Tx public key: cc5da716b87062251cd642f142b820355912a245dd9d4bbc2def3f3c685bc3e8
Timestamp: 1582515214 Timestamp [UCT]: 2020-02-24 03:33:34 Age [y:d:h:m:s]: 04:308:16:54:25
Block: 71356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113167 RingCT/type: yes/0
Extra: 01cc5da716b87062251cd642f142b820355912a245dd9d4bbc2def3f3c685bc3e802110000000103d36d11000000000000000000

1 output(s) for total of 356.097358731000 dcy

stealth address amount amount idx
00: 825945f630a0a680d27cb18c6ebb2f2ad86452a1af98f94110ffbf18b8cfca4c 356.097358731000 131805 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": 71366, "vin": [ { "gen": { "height": 71356 } } ], "vout": [ { "amount": 356097358731, "target": { "key": "825945f630a0a680d27cb18c6ebb2f2ad86452a1af98f94110ffbf18b8cfca4c" } } ], "extra": [ 1, 204, 93, 167, 22, 184, 112, 98, 37, 28, 214, 66, 241, 66, 184, 32, 53, 89, 18, 162, 69, 221, 157, 75, 188, 45, 239, 63, 60, 104, 91, 195, 232, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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