Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 927babb8591118b260185a6087562b68a8fd07a0b95ce864548da0fc1f642561

Tx prefix hash: 0810213b7eff26236ab894658b746d2a14d29cfb1f514b331b081106134966b6
Tx public key: 336441f7fb47f1157423e5eef4b34f3d4a72ac61ebd5cb7d6ddaccd9cef0d8a3
Timestamp: 1746756265 Timestamp [UCT]: 2025-05-09 02:04:25 Age [y:d:h:m:s]: 00:194:07:33:52
Block: 1278844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136588 RingCT/type: yes/0
Extra: 01336441f7fb47f1157423e5eef4b34f3d4a72ac61ebd5cb7d6ddaccd9cef0d8a30211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fea45e94e76f5ef3b21e40c5ba3674e0f4bf3077fcee566bbff16b94fe88506 0.600000000000 1766215 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": 1278854, "vin": [ { "gen": { "height": 1278844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fea45e94e76f5ef3b21e40c5ba3674e0f4bf3077fcee566bbff16b94fe88506" } } ], "extra": [ 1, 51, 100, 65, 247, 251, 71, 241, 21, 116, 35, 229, 238, 244, 179, 79, 61, 74, 114, 172, 97, 235, 213, 203, 125, 109, 218, 204, 217, 206, 240, 216, 163, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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