Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67d0e68ba77a57b7d81142f833983c89f16b85467af6508c80403062918b8fd

Tx prefix hash: 2ded9dc6fa0fbb6bae2a84b2189f9fd0260d3149083b81b8a1e9c2ed6a8edd27
Tx public key: ffdf86754d49da87067c5a9c75dbd9c97479096b4c64bebf953e3673c000fdc2
Timestamp: 1735329340 Timestamp [UCT]: 2024-12-27 19:55:40 Age [y:d:h:m:s]: 00:279:23:08:24
Block: 1184516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197547 RingCT/type: yes/0
Extra: 01ffdf86754d49da87067c5a9c75dbd9c97479096b4c64bebf953e3673c000fdc202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1544e74254c1a921a9ee3fc92e9acd61e25a7157d113df24989f10239073e29 0.600000000000 1670973 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": 1184526, "vin": [ { "gen": { "height": 1184516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1544e74254c1a921a9ee3fc92e9acd61e25a7157d113df24989f10239073e29" } } ], "extra": [ 1, 255, 223, 134, 117, 77, 73, 218, 135, 6, 124, 90, 156, 117, 219, 217, 201, 116, 121, 9, 107, 76, 100, 190, 191, 149, 62, 54, 115, 192, 0, 253, 194, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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