Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4366aadb2fb9cf8c3f5b2c43ef844b19875ea674f50ea5a4a2fc1a27975951d7

Tx prefix hash: 35894020d8a92aa16488a6912577bd4cd964ca67251447e702ad8576b15a9f20
Tx public key: e2be7d60e50aa517f87ed1cb760e1f9e9234c67493e7459f5125e938074a9869
Timestamp: 1724985290 Timestamp [UCT]: 2024-08-30 02:34:50 Age [y:d:h:m:s]: 00:268:12:34:11
Block: 1098881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191817 RingCT/type: yes/0
Extra: 01e2be7d60e50aa517f87ed1cb760e1f9e9234c67493e7459f5125e938074a986902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 167547630d92781e2662caaae64b5e0840645d1765291028831149638b044fa4 0.600000000000 1574748 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": 1098891, "vin": [ { "gen": { "height": 1098881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167547630d92781e2662caaae64b5e0840645d1765291028831149638b044fa4" } } ], "extra": [ 1, 226, 190, 125, 96, 229, 10, 165, 23, 248, 126, 209, 203, 118, 14, 31, 158, 146, 52, 198, 116, 147, 231, 69, 159, 81, 37, 233, 56, 7, 74, 152, 105, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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