Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b540419916d308ab971e2eda84acd38948ebdff745512dd8e491496067a6858

Tx prefix hash: 83534838b827c724e9d5d4aa5f6a78fe3d0acb9f302d3962bd21cff5a7796664
Tx public key: 8a1bd85fbb302c8a0759491064ac3c1967371d8c04143dfdb9c9759dc6705ed0
Timestamp: 1723495896 Timestamp [UCT]: 2024-08-12 20:51:36 Age [y:d:h:m:s]: 00:264:21:25:03
Block: 1086530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189220 RingCT/type: yes/0
Extra: 018a1bd85fbb302c8a0759491064ac3c1967371d8c04143dfdb9c9759dc6705ed0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13c6694e231a41eae3f5d7abd3c833ccb4db1969e9bfaeab99c1ba3d98caa059 0.600000000000 1561127 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": 1086540, "vin": [ { "gen": { "height": 1086530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13c6694e231a41eae3f5d7abd3c833ccb4db1969e9bfaeab99c1ba3d98caa059" } } ], "extra": [ 1, 138, 27, 216, 95, 187, 48, 44, 138, 7, 89, 73, 16, 100, 172, 60, 25, 103, 55, 29, 140, 4, 20, 61, 253, 185, 201, 117, 157, 198, 112, 94, 208, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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