Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6aad764baf2810159e7967ad9f254e0bb1fd20b2accab74beb250f3833b76c

Tx prefix hash: c6c0f87a599900b97df5cab5d96d103e3fc23d85ea7ada886990c4f8c52c6751
Tx public key: b6807ea5dceb1124e9534fa6e42f963968c52befd1a66e869ffeaba40c97c9a8
Timestamp: 1717342017 Timestamp [UCT]: 2024-06-02 15:26:57 Age [y:d:h:m:s]: 01:158:16:30:43
Block: 1035526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371989 RingCT/type: yes/0
Extra: 01b6807ea5dceb1124e9534fa6e42f963968c52befd1a66e869ffeaba40c97c9a802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d1b65d32ff17287092cc8aa801375aa64cea6929e5baafe789fdb7ad843b6a 0.600000000000 1504047 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": 1035536, "vin": [ { "gen": { "height": 1035526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d1b65d32ff17287092cc8aa801375aa64cea6929e5baafe789fdb7ad843b6a" } } ], "extra": [ 1, 182, 128, 126, 165, 220, 235, 17, 36, 233, 83, 79, 166, 228, 47, 150, 57, 104, 197, 43, 239, 209, 166, 110, 134, 159, 254, 171, 164, 12, 151, 201, 168, 2, 17, 0, 0, 0, 1, 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