Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43382548f73029d966ccf0b84dc46b2dbd62e00409b4fce91cdad4da10a65731

Tx prefix hash: 10d03f98e582dcafc0434b238bfdfd737a9a3b11b86b63f63c9b9cbba0a14c77
Tx public key: 4de02fd048d1f2cc9a3146a90b318b6518d7e23d48f2a504907f56f545b03aa7
Timestamp: 1657614670 Timestamp [UCT]: 2022-07-12 08:31:10 Age [y:d:h:m:s]: 03:112:08:33:45
Block: 542050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 860016 RingCT/type: yes/0
Extra: 014de02fd048d1f2cc9a3146a90b318b6518d7e23d48f2a504907f56f545b03aa702110000000175e3f0e9000000000000000000

1 output(s) for total of 9.816773870000 dcy

stealth address amount amount idx
00: 704aeb0cdddd310f67232fe664a06ecf8a14effc5b8f92f4f8ba1171a05afa77 9.816773870000 972553 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": 542060, "vin": [ { "gen": { "height": 542050 } } ], "vout": [ { "amount": 9816773870, "target": { "key": "704aeb0cdddd310f67232fe664a06ecf8a14effc5b8f92f4f8ba1171a05afa77" } } ], "extra": [ 1, 77, 224, 47, 208, 72, 209, 242, 204, 154, 49, 70, 169, 11, 49, 139, 101, 24, 215, 226, 61, 72, 242, 165, 4, 144, 127, 86, 245, 69, 176, 58, 167, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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