Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279fc114ddfc469c9cdac7ce5427bbcf82c69d000c69d0c4572164b02a618a20

Tx prefix hash: 13e5385372c55b8e1af50482001d03c977e68b4b17859f466312bf7ff9b9e6b0
Tx public key: 11e51724264fbeedcc7eaa191b7045c5dbccd5d509d264f4e46ef6867e85237e
Timestamp: 1708159687 Timestamp [UCT]: 2024-02-17 08:48:07 Age [y:d:h:m:s]: 01:043:18:33:38
Block: 959387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292310 RingCT/type: yes/0
Extra: 0111e51724264fbeedcc7eaa191b7045c5dbccd5d509d264f4e46ef6867e85237e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b14d0dfcf08582824378d4acefc7ba19eb68dc4c1557bff792f8807b7a5ea8 0.600000000000 1418922 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": 959397, "vin": [ { "gen": { "height": 959387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b14d0dfcf08582824378d4acefc7ba19eb68dc4c1557bff792f8807b7a5ea8" } } ], "extra": [ 1, 17, 229, 23, 36, 38, 79, 190, 237, 204, 126, 170, 25, 27, 112, 69, 197, 219, 204, 213, 213, 9, 210, 100, 244, 228, 110, 246, 134, 126, 133, 35, 126, 2, 17, 0, 0, 0, 1, 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