Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a044de67795327f8a9ac2924e98d5eec5206a9405b7f67b49135b0618c9e49

Tx prefix hash: 2a0910eac2a7510bb31f06771bff73ed6d6b5611d5771e2bc553e071efa0b619
Tx public key: 09324dbee09c82a732b12efd13cbf3c5fe0ccbbb05211117e06085342891d4a0
Timestamp: 1749758368 Timestamp [UCT]: 2025-06-12 19:59:28 Age [y:d:h:m:s]: 00:149:07:53:39
Block: 1303670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104438 RingCT/type: yes/0
Extra: 0109324dbee09c82a732b12efd13cbf3c5fe0ccbbb05211117e06085342891d4a002110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b8054c6b0ca106ec8af5f14a45f8fea1f4e96a29fb45b00c29a8db5550a9be 0.600000000000 1791253 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": 1303680, "vin": [ { "gen": { "height": 1303670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b8054c6b0ca106ec8af5f14a45f8fea1f4e96a29fb45b00c29a8db5550a9be" } } ], "extra": [ 1, 9, 50, 77, 190, 224, 156, 130, 167, 50, 177, 46, 253, 19, 203, 243, 197, 254, 12, 203, 187, 5, 33, 17, 23, 224, 96, 133, 52, 40, 145, 212, 160, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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