Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58866b603d136006314b98131b31b4f2969b301ad437f57c07823c7bd652444d

Tx prefix hash: 27607ec334d747370d38885728cc0bbb6b33f759cda211c03599f27f14a1ef1c
Tx public key: b2cba57eccdc896245b7f8af9a9a616d2c9285cff1baf0866c41bd97b25c865b
Timestamp: 1631607425 Timestamp [UCT]: 2021-09-14 08:17:05 Age [y:d:h:m:s]: 03:260:12:56:46
Block: 333496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 961672 RingCT/type: yes/0
Extra: 01b2cba57eccdc896245b7f8af9a9a616d2c9285cff1baf0866c41bd97b25c865b021100000010f29d7abf000000000000000000

1 output(s) for total of 48.193642600000 dcy

stealth address amount amount idx
00: f53a5b5e104246a2aa994616ff4d0096ef2eeeb72106b23b2aeca803a3ce4455 48.193642600000 688169 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": 333506, "vin": [ { "gen": { "height": 333496 } } ], "vout": [ { "amount": 48193642600, "target": { "key": "f53a5b5e104246a2aa994616ff4d0096ef2eeeb72106b23b2aeca803a3ce4455" } } ], "extra": [ 1, 178, 203, 165, 126, 204, 220, 137, 98, 69, 183, 248, 175, 154, 154, 97, 109, 44, 146, 133, 207, 241, 186, 240, 134, 108, 65, 189, 151, 178, 92, 134, 91, 2, 17, 0, 0, 0, 16, 242, 157, 122, 191, 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