Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecfefa96d5fb4fa39c76f0f7baf179b67d8a935ae584ed833fbb6787633b5371

Tx prefix hash: b1e76380cdf5ecdbf19069202b1058456446d92c3f2468ab6d7e3c4dac7d7447
Tx public key: 4120e5360a5da2f9f8cbf07d80afec2b0b05fe6689bbe770a48a505dd76baac5
Timestamp: 1710768945 Timestamp [UCT]: 2024-03-18 13:35:45 Age [y:d:h:m:s]: 01:068:12:15:58
Block: 981044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309972 RingCT/type: yes/0
Extra: 014120e5360a5da2f9f8cbf07d80afec2b0b05fe6689bbe770a48a505dd76baac502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8e9e461fa9521bfdd730f346e0c30fde6bb5ce83e54ea415ddc0017fa38028 0.600000000000 1441129 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": 981054, "vin": [ { "gen": { "height": 981044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8e9e461fa9521bfdd730f346e0c30fde6bb5ce83e54ea415ddc0017fa38028" } } ], "extra": [ 1, 65, 32, 229, 54, 10, 93, 162, 249, 248, 203, 240, 125, 128, 175, 236, 43, 11, 5, 254, 102, 137, 187, 231, 112, 164, 138, 80, 93, 215, 107, 170, 197, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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