Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7757f24d8c65870d798d5f97c187def9518ffb03653874b604b0bb4b8b86f815

Tx prefix hash: 852e968d5dfdfb5cdd22e805ced807334ef57d8df720c3d032c38aca9852a6b8
Tx public key: a328e5c224bb3e7e7564388a38bc8d3e2cad10f4325c7752f06c5004fa747af4
Timestamp: 1730861792 Timestamp [UCT]: 2024-11-06 02:56:32 Age [y:d:h:m:s]: 00:001:04:27:11
Block: 1147514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 854 RingCT/type: yes/0
Extra: 01a328e5c224bb3e7e7564388a38bc8d3e2cad10f4325c7752f06c5004fa747af4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129d4f858f8f82446dfe11b12cc55b112b12fd525537d3b67e12c442cdc3a402 0.600000000000 1632213 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": 1147524, "vin": [ { "gen": { "height": 1147514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129d4f858f8f82446dfe11b12cc55b112b12fd525537d3b67e12c442cdc3a402" } } ], "extra": [ 1, 163, 40, 229, 194, 36, 187, 62, 126, 117, 100, 56, 138, 56, 188, 141, 62, 44, 173, 16, 244, 50, 92, 119, 82, 240, 108, 80, 4, 250, 116, 122, 244, 2, 17, 0, 0, 0, 3, 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