Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7703409e24649033ce8f071766a385ee133eb7b1c7ce2ca258812aa345441e81

Tx prefix hash: c9e1711af4042f83aedf96fc11a7057d053f907390b28dc39f45944fb5693ef4
Tx public key: 080b29a9089efc7a6dcfb3a88e98b046cf53b9f66d0e457589ee713cde83da3d
Timestamp: 1627559913 Timestamp [UCT]: 2021-07-29 11:58:33 Age [y:d:h:m:s]: 04:096:08:09:53
Block: 303137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099729 RingCT/type: yes/0
Extra: 01080b29a9089efc7a6dcfb3a88e98b046cf53b9f66d0e457589ee713cde83da3d02110000002c01f1e57f000000000000000000

1 output(s) for total of 60.754963843000 dcy

stealth address amount amount idx
00: b980b910d0d18e9f17242e1049f82689d9e4a6ffb8e6a3d039958a7aef78213d 60.754963843000 632738 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": 303147, "vin": [ { "gen": { "height": 303137 } } ], "vout": [ { "amount": 60754963843, "target": { "key": "b980b910d0d18e9f17242e1049f82689d9e4a6ffb8e6a3d039958a7aef78213d" } } ], "extra": [ 1, 8, 11, 41, 169, 8, 158, 252, 122, 109, 207, 179, 168, 142, 152, 176, 70, 207, 83, 185, 246, 109, 14, 69, 117, 137, 238, 113, 60, 222, 131, 218, 61, 2, 17, 0, 0, 0, 44, 1, 241, 229, 127, 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