Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a4d50e1bd577a4dd97fd194c340be627083cd11ca9198363b522cf33d691e87

Tx prefix hash: 69f0fa26b231c1cff3eba5abdbe9fa679aa00b369a81073c2560214ad49b6d78
Tx public key: aa8825dea1a040f1f8755ca30f3e43776133cb01cfbc5b32df6e70fb81d9029d
Timestamp: 1750292183 Timestamp [UCT]: 2025-06-19 00:16:23 Age [y:d:h:m:s]: 00:154:18:41:57
Block: 1307996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108434 RingCT/type: yes/0
Extra: 01aa8825dea1a040f1f8755ca30f3e43776133cb01cfbc5b32df6e70fb81d9029d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50c4d5ebe2705881e50d9ef73bb47fca273c8fb9cd23d87034c4cb3aabeec6fc 0.600000000000 1795607 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": 1308006, "vin": [ { "gen": { "height": 1307996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50c4d5ebe2705881e50d9ef73bb47fca273c8fb9cd23d87034c4cb3aabeec6fc" } } ], "extra": [ 1, 170, 136, 37, 222, 161, 160, 64, 241, 248, 117, 92, 163, 15, 62, 67, 119, 97, 51, 203, 1, 207, 188, 91, 50, 223, 110, 112, 251, 129, 217, 2, 157, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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