Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6457c627416ebdd51f7359821f636a1c32cefd6a3171d7c8cb2d94aa4206547e

Tx prefix hash: 75563336afe29041f062fca96bceee4de13a034f962b8d98b2e11132a6a9af89
Tx public key: b464841995b6b9641bdf9a993dd7d1dd53fdc136b13e81d10a9e332d66d96340
Timestamp: 1581471622 Timestamp [UCT]: 2020-02-12 01:40:22 Age [y:d:h:m:s]: 05:033:03:11:30
Block: 63067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176540 RingCT/type: yes/0
Extra: 01b464841995b6b9641bdf9a993dd7d1dd53fdc136b13e81d10a9e332d66d963400211000000094943cd9f000000000000000000

1 output(s) for total of 379.352617093000 dcy

stealth address amount amount idx
00: f5dd3683589378393104f441ad7f070f3bf5d13c9cc895190d29858b453b1a84 379.352617093000 116306 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": 63077, "vin": [ { "gen": { "height": 63067 } } ], "vout": [ { "amount": 379352617093, "target": { "key": "f5dd3683589378393104f441ad7f070f3bf5d13c9cc895190d29858b453b1a84" } } ], "extra": [ 1, 180, 100, 132, 25, 149, 182, 185, 100, 27, 223, 154, 153, 61, 215, 209, 221, 83, 253, 193, 54, 177, 62, 129, 209, 10, 158, 51, 45, 102, 217, 99, 64, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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