Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b5c3f10d7442428f10a514ef53e30e907132e818ce303430e2956379b68a5f

Tx prefix hash: 57b6a7ebb53a0acb1b04fb5adaa78fde1d953c0b8b91c4af75a1f35469ca0afd
Tx public key: 276082b7b1aced723c858adcdcc221a6cc0d2a12645f5878cdf898ea18c5d016
Timestamp: 1762957560 Timestamp [UCT]: 2025-11-12 14:26:00 Age [y:d:h:m:s]: 00:041:05:44:36
Block: 1410573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29514 RingCT/type: yes/0
Extra: 01276082b7b1aced723c858adcdcc221a6cc0d2a12645f5878cdf898ea18c5d01602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd655f92fe7761d513cdc89dfee80afd64b6c37759ad41538cdfee8ebf7162ee 0.600000000000 1899026 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": 1410583, "vin": [ { "gen": { "height": 1410573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd655f92fe7761d513cdc89dfee80afd64b6c37759ad41538cdfee8ebf7162ee" } } ], "extra": [ 1, 39, 96, 130, 183, 177, 172, 237, 114, 60, 133, 138, 220, 220, 194, 33, 166, 204, 13, 42, 18, 100, 95, 88, 120, 205, 248, 152, 234, 24, 197, 208, 22, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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