Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e97dbd4e6bded424d13137eb330511d6dd17ef54f92593d15f9d58d0bea8e157

Tx prefix hash: e5027a88507f3b3cd56929be5d6a37ab72203a4859b063135088c1e7ae0f47ce
Tx public key: 582d6d289c17c6a557417a84f8c375c481afaaa5b1970f5792e46c8d54e458fe
Timestamp: 1720282467 Timestamp [UCT]: 2024-07-06 16:14:27 Age [y:d:h:m:s]: 00:316:03:45:39
Block: 1059900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225918 RingCT/type: yes/0
Extra: 01582d6d289c17c6a557417a84f8c375c481afaaa5b1970f5792e46c8d54e458fe02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae966e18d51f1f584ad9cf1912ed9e0101dd7cd78e826cffc4e8d50e2ba536c6 0.600000000000 1530371 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": 1059910, "vin": [ { "gen": { "height": 1059900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae966e18d51f1f584ad9cf1912ed9e0101dd7cd78e826cffc4e8d50e2ba536c6" } } ], "extra": [ 1, 88, 45, 109, 40, 156, 23, 198, 165, 87, 65, 122, 132, 248, 195, 117, 196, 129, 175, 170, 165, 177, 151, 15, 87, 146, 228, 108, 141, 84, 228, 88, 254, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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