Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d7b8b1fb59028ee71240e441146a5590e1f5409e27d92e3f199127e1dfc70ca

Tx prefix hash: b8d1733847027ed5d8f0238a741f5f3f66884aaa9dcd217b5e1b08fbb70009a2
Tx public key: 71e3b2ebf42f72f1de5baeac1149b0b2e52af2dd9332a346aa23c8bd369e8126
Timestamp: 1760103025 Timestamp [UCT]: 2025-10-10 13:30:25 Age [y:d:h:m:s]: 00:048:17:44:31
Block: 1386912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34899 RingCT/type: yes/0
Extra: 0171e3b2ebf42f72f1de5baeac1149b0b2e52af2dd9332a346aa23c8bd369e8126021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60b0a4f0a09a5856d71daeb493cafca18373044e119a6dd72f632277d228bdeb 0.600000000000 1875089 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": 1386922, "vin": [ { "gen": { "height": 1386912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60b0a4f0a09a5856d71daeb493cafca18373044e119a6dd72f632277d228bdeb" } } ], "extra": [ 1, 113, 227, 178, 235, 244, 47, 114, 241, 222, 91, 174, 172, 17, 73, 176, 178, 229, 42, 242, 221, 147, 50, 163, 70, 170, 35, 200, 189, 54, 158, 129, 38, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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