Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e43d77735431be13b974ede7ad40b1477d7ede185e635e0039b77d08f45c96de

Tx prefix hash: 9e13cf720c80d90ed33e3bd63375c2a80d8857c1ca27196ff95e9214e683bd93
Tx public key: 313b2fd3d5ecfe8dfca08df0850a9db1a7c63d29f81015fb54182db0d4356431
Timestamp: 1741436030 Timestamp [UCT]: 2025-03-08 12:13:50 Age [y:d:h:m:s]: 00:256:14:01:34
Block: 1234821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181116 RingCT/type: yes/0
Extra: 01313b2fd3d5ecfe8dfca08df0850a9db1a7c63d29f81015fb54182db0d435643102110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5bc43951bfea0bbced4294be75a4fc968f25a5fe15beb0abb4a3f5a8a685c35 0.600000000000 1721756 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": 1234831, "vin": [ { "gen": { "height": 1234821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5bc43951bfea0bbced4294be75a4fc968f25a5fe15beb0abb4a3f5a8a685c35" } } ], "extra": [ 1, 49, 59, 47, 211, 213, 236, 254, 141, 252, 160, 141, 240, 133, 10, 157, 177, 167, 198, 61, 41, 248, 16, 21, 251, 84, 24, 45, 176, 212, 53, 100, 49, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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