Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd787b364bc99b004c3597e5c41ae67c4a185bbf3d99895f2eb0c72ea1ee968a

Tx prefix hash: cb8eaa1815bedd6a29a345a0606b2d6b924a2e2cd0e7648b19681f7186f03c6e
Tx public key: 113129301ffeba6ed1f823331d109af9c613d3ce09407c8c549995f1882c400c
Timestamp: 1751468550 Timestamp [UCT]: 2025-07-02 15:02:30 Age [y:d:h:m:s]: 00:210:04:01:32
Block: 1317295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148366 RingCT/type: yes/0
Extra: 01113129301ffeba6ed1f823331d109af9c613d3ce09407c8c549995f1882c400c021100000034bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a0c7abd8bcb8e19a3b66e5f3711045e58862c7a82ab55a0c505adaf6fb5040 0.600000000000 1804962 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": 1317305, "vin": [ { "gen": { "height": 1317295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a0c7abd8bcb8e19a3b66e5f3711045e58862c7a82ab55a0c505adaf6fb5040" } } ], "extra": [ 1, 17, 49, 41, 48, 31, 254, 186, 110, 209, 248, 35, 51, 29, 16, 154, 249, 198, 19, 211, 206, 9, 64, 124, 140, 84, 153, 149, 241, 136, 44, 64, 12, 2, 17, 0, 0, 0, 52, 191, 81, 178, 162, 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