Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 643e2e6b63c5b9239c8ba36adb48fe12c11ac45073fbbb41b35ab4d558ab09d8

Tx prefix hash: 5e17838fa95659ae0eb181378c746f81883e22538dc099aa73b0c6bbb3ea543d
Tx public key: 306e750f307225a3b6575ba6e5b6a147e07870ec1297f40facd122d076450456
Timestamp: 1578317388 Timestamp [UCT]: 2020-01-06 13:29:48 Age [y:d:h:m:s]: 05:001:23:42:15
Block: 39697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151789 RingCT/type: yes/0
Extra: 01306e750f307225a3b6575ba6e5b6a147e07870ec1297f40facd122d076450456021100000105ff58ae94000000000000000000

1 output(s) for total of 453.386107057000 dcy

stealth address amount amount idx
00: 8ed07a2de241bb48deb0f5ea59bf9a773e2e562a4285dff1e0b1412e52d74534 453.386107057000 68857 of 0

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": 39707, "vin": [ { "gen": { "height": 39697 } } ], "vout": [ { "amount": 453386107057, "target": { "key": "8ed07a2de241bb48deb0f5ea59bf9a773e2e562a4285dff1e0b1412e52d74534" } } ], "extra": [ 1, 48, 110, 117, 15, 48, 114, 37, 163, 182, 87, 91, 166, 229, 182, 161, 71, 224, 120, 112, 236, 18, 151, 244, 15, 172, 209, 34, 208, 118, 69, 4, 86, 2, 17, 0, 0, 1, 5, 255, 88, 174, 148, 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