Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc93774cc93c31dabc1b03e49ba79dd97009315349c1b330da608cbacc0c99f

Tx prefix hash: 31a8db27315c3759eb4a87dd346eae4f2c0a96746c84319c5dfded57e76b5ea1
Tx public key: 3784dd4a1649fefabffa1b23a49c437e5e88c4e443e5a874352f6fce5a6358e4
Timestamp: 1734730817 Timestamp [UCT]: 2024-12-20 21:40:17 Age [y:d:h:m:s]: 00:015:08:52:26
Block: 1179593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10975 RingCT/type: yes/0
Extra: 013784dd4a1649fefabffa1b23a49c437e5e88c4e443e5a874352f6fce5a6358e402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f9e2783ce834e4715235270a12ed27e26ebcf3630e66e85f1f775d6284fa524 0.600000000000 1665992 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": 1179603, "vin": [ { "gen": { "height": 1179593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f9e2783ce834e4715235270a12ed27e26ebcf3630e66e85f1f775d6284fa524" } } ], "extra": [ 1, 55, 132, 221, 74, 22, 73, 254, 250, 191, 250, 27, 35, 164, 156, 67, 126, 94, 136, 196, 228, 67, 229, 168, 116, 53, 47, 111, 206, 90, 99, 88, 228, 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