Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12688df47aedd08d7116d35b959c3176e65c33a05daa3307358993f0f11e02b

Tx prefix hash: ad0f3278284f10ef00fbe6856d056ca8f2b1db238ced04e1d530c2fe79d89179
Tx public key: ec0a7373416c3da0e3214f3b0016bb69709a1f3f5717c86329d44d0ea87281cb
Timestamp: 1730734830 Timestamp [UCT]: 2024-11-04 15:40:30 Age [y:d:h:m:s]: 00:064:07:28:38
Block: 1146467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46012 RingCT/type: yes/0
Extra: 01ec0a7373416c3da0e3214f3b0016bb69709a1f3f5717c86329d44d0ea87281cb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b4196d6e9610a0c119a479b2cd57990b013c0e0e0fa5aaa8828bd2907fa80d 0.600000000000 1631112 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": 1146477, "vin": [ { "gen": { "height": 1146467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b4196d6e9610a0c119a479b2cd57990b013c0e0e0fa5aaa8828bd2907fa80d" } } ], "extra": [ 1, 236, 10, 115, 115, 65, 108, 61, 160, 227, 33, 79, 59, 0, 22, 187, 105, 112, 154, 31, 63, 87, 23, 200, 99, 41, 212, 77, 14, 168, 114, 129, 203, 2, 17, 0, 0, 0, 1, 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