Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cbe3c00e4951873f87ad4cdcd95b3f678bbdecd9223efc77ee77a00acbe4466

Tx prefix hash: 232cf554bf3916408709af2a373e679d54e9fd909f5136b182639bb29ed900aa
Tx public key: 7b9ca5b3a8207aeaecf5b01e2738c411a4c3e666dff321e8bc593e40707df5e5
Timestamp: 1637985042 Timestamp [UCT]: 2021-11-27 03:50:42 Age [y:d:h:m:s]: 03:339:13:41:25
Block: 382989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1019093 RingCT/type: yes/0
Extra: 017b9ca5b3a8207aeaecf5b01e2738c411a4c3e666dff321e8bc593e40707df5e50211000000044a0f5013000000000000000000

1 output(s) for total of 33.037625334000 dcy

stealth address amount amount idx
00: b826bf7eaae95da4b3d2de623ef32a8e24e9986f1ecb05d99f02b508d53fbee3 33.037625334000 773306 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": 382999, "vin": [ { "gen": { "height": 382989 } } ], "vout": [ { "amount": 33037625334, "target": { "key": "b826bf7eaae95da4b3d2de623ef32a8e24e9986f1ecb05d99f02b508d53fbee3" } } ], "extra": [ 1, 123, 156, 165, 179, 168, 32, 122, 234, 236, 245, 176, 30, 39, 56, 196, 17, 164, 195, 230, 102, 223, 243, 33, 232, 188, 89, 62, 64, 112, 125, 245, 229, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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