Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 065110cb2aa63f6219224b4e4d5f999f089f9b9c09037fadafef2df2545aea02

Tx prefix hash: 7464e2c342d81858e5620b46683e02cd98430777a89ba67a1ab2b053efb82db6
Tx public key: e836a6597bc1712d1e17bfdf05a8e77017d66a55155fed8a89c1e4f27300b302
Timestamp: 1715409158 Timestamp [UCT]: 2024-05-11 06:32:38 Age [y:d:h:m:s]: 00:348:20:41:47
Block: 1019520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249354 RingCT/type: yes/0
Extra: 01e836a6597bc1712d1e17bfdf05a8e77017d66a55155fed8a89c1e4f27300b30202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8820161f0f30ee8874ef750b81dc251a972b09702cd3a0c5e3ea528d7f440752 0.600000000000 1483509 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": 1019530, "vin": [ { "gen": { "height": 1019520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8820161f0f30ee8874ef750b81dc251a972b09702cd3a0c5e3ea528d7f440752" } } ], "extra": [ 1, 232, 54, 166, 89, 123, 193, 113, 45, 30, 23, 191, 223, 5, 168, 231, 112, 23, 214, 106, 85, 21, 95, 237, 138, 137, 193, 228, 242, 115, 0, 179, 2, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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