Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d32ad0cb5f1e32dad5f99a61fb22f42e8ef40f7f9cd3e735ab22948b9553ab1

Tx prefix hash: 2077413238232fbf70b434e4f3348fc8cb8276ab44a02f356b1925560b543a7c
Tx public key: 5cf0ed7ff68f481266191a9677fc0c12c8cbd02412b2d6417dc632fa33c8ed03
Timestamp: 1758243005 Timestamp [UCT]: 2025-09-19 00:50:05 Age [y:d:h:m:s]: 00:057:14:30:05
Block: 1371501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41239 RingCT/type: yes/0
Extra: 015cf0ed7ff68f481266191a9677fc0c12c8cbd02412b2d6417dc632fa33c8ed03021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35b355c8e7e175363e4c8931cadc5f826f19e3a9a5869d7c458df1e756e4bef 0.600000000000 1859578 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": 1371511, "vin": [ { "gen": { "height": 1371501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35b355c8e7e175363e4c8931cadc5f826f19e3a9a5869d7c458df1e756e4bef" } } ], "extra": [ 1, 92, 240, 237, 127, 246, 143, 72, 18, 102, 25, 26, 150, 119, 252, 12, 18, 200, 203, 208, 36, 18, 178, 214, 65, 125, 198, 50, 250, 51, 200, 237, 3, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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