Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d57c7061e1b4575f18070f2c070ccd5460261d3eeeae6dfc32f0542856726877

Tx prefix hash: f87604c461e6bb30000a4f24d453fdf185c18ce3a1f52f412ff0566f0a66dd05
Tx public key: 368bffbacb3493c3c7bba914a9ffc36adf4a3010f677af749aa67f7938f73d9e
Timestamp: 1736109932 Timestamp [UCT]: 2025-01-05 20:45:32 Age [y:d:h:m:s]: 00:298:15:21:57
Block: 1190988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210928 RingCT/type: yes/0
Extra: 01368bffbacb3493c3c7bba914a9ffc36adf4a3010f677af749aa67f7938f73d9e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b901403b4a48cd7aee757b5dfcf665ee9cbfea1be75b6484b4e75d19b3fdca87 0.600000000000 1677511 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": 1190998, "vin": [ { "gen": { "height": 1190988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b901403b4a48cd7aee757b5dfcf665ee9cbfea1be75b6484b4e75d19b3fdca87" } } ], "extra": [ 1, 54, 139, 255, 186, 203, 52, 147, 195, 199, 187, 169, 20, 169, 255, 195, 106, 223, 74, 48, 16, 246, 119, 175, 116, 154, 166, 127, 121, 56, 247, 61, 158, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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