Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf10c09ee6825a72928ceb9a721b1b58092b1bfa38a47de401f93ee0a17317d4

Tx prefix hash: a6356e048116d7e34766e79109d622c72e59a1d9e094883c2730c1a3b3a214d7
Tx public key: c93cf0e07c7bdf300297f50502771a8810b6d0dbfc49d53952eae24a05f9e9f8
Timestamp: 1577949420 Timestamp [UCT]: 2020-01-02 07:17:00 Age [y:d:h:m:s]: 05:304:02:05:26
Block: 37009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1364834 RingCT/type: yes/0
Extra: 01c93cf0e07c7bdf300297f50502771a8810b6d0dbfc49d53952eae24a05f9e9f80211000000094ac5aa02000000000000000000

1 output(s) for total of 462.780096013000 dcy

stealth address amount amount idx
00: c516a4318a16c14b7309ee52a50008f08cd7fd6bf394668edcd8beac7c97d91f 462.780096013000 62763 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": 37019, "vin": [ { "gen": { "height": 37009 } } ], "vout": [ { "amount": 462780096013, "target": { "key": "c516a4318a16c14b7309ee52a50008f08cd7fd6bf394668edcd8beac7c97d91f" } } ], "extra": [ 1, 201, 60, 240, 224, 124, 123, 223, 48, 2, 151, 245, 5, 2, 119, 26, 136, 16, 182, 208, 219, 252, 73, 213, 57, 82, 234, 226, 74, 5, 249, 233, 248, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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