Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62fc0cb5040e513f80278b89bb1d11e418dda75d1dab2d8932fcb6dbde751f1

Tx prefix hash: a3fd0e7b9fbe023d97ce53051cc674f3dcea77aa2cdc93b9299bc3793bad54d8
Tx public key: 2e18ab66eddcdcce702991c9230f73f943afd2fccce8e32a1f2e1bd1c28b3681
Timestamp: 1730492377 Timestamp [UCT]: 2024-11-01 20:19:37 Age [y:d:h:m:s]: 01:007:14:31:36
Block: 1144450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263866 RingCT/type: yes/0
Extra: 012e18ab66eddcdcce702991c9230f73f943afd2fccce8e32a1f2e1bd1c28b3681021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2db33cf1c96312444d379484ab67eeb1ae84c0c1606824eaa1bd4d7bd389a7fb 0.600000000000 1628673 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": 1144460, "vin": [ { "gen": { "height": 1144450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2db33cf1c96312444d379484ab67eeb1ae84c0c1606824eaa1bd4d7bd389a7fb" } } ], "extra": [ 1, 46, 24, 171, 102, 237, 220, 220, 206, 112, 41, 145, 201, 35, 15, 115, 249, 67, 175, 210, 252, 204, 232, 227, 42, 31, 46, 27, 209, 194, 139, 54, 129, 2, 17, 0, 0, 0, 2, 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