Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970a9dd5f7307ecdc79a903df609e8bf84b41271e53b39718b76d74815ce7125

Tx prefix hash: bffc50969a746adcce0bb24b8ca886b5f5990259e5ca3dc9c7d78c0cb2187624
Tx public key: 0a0d8c5eede93412ddca0e25cd448a595d044539744cae3da5cbb21d2e37ab63
Timestamp: 1745586209 Timestamp [UCT]: 2025-04-25 13:03:29 Age [y:d:h:m:s]: 00:202:15:42:29
Block: 1269163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142549 RingCT/type: yes/0
Extra: 010a0d8c5eede93412ddca0e25cd448a595d044539744cae3da5cbb21d2e37ab63021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8d19526280c3633dc245499267d1ab868f601bd914265bb2d5c628d1f55f6a 0.600000000000 1756398 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": 1269173, "vin": [ { "gen": { "height": 1269163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8d19526280c3633dc245499267d1ab868f601bd914265bb2d5c628d1f55f6a" } } ], "extra": [ 1, 10, 13, 140, 94, 237, 233, 52, 18, 221, 202, 14, 37, 205, 68, 138, 89, 93, 4, 69, 57, 116, 76, 174, 61, 165, 203, 178, 29, 46, 55, 171, 99, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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