Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 307cd4917a631769fcae610935330c0de7deaa02931c5c3217cf37c6fab2c24e

Tx prefix hash: f577675d3ec22400d7ca2a109332f37269c2e42ee7bd90262cecf3f1450b6d15
Tx public key: 6b1507e16e6f051831f33f680c096052a0771cfbaf2654903d1de8216a70ce9f
Timestamp: 1639012179 Timestamp [UCT]: 2021-12-09 01:09:39 Age [y:d:h:m:s]: 02:353:10:19:39
Block: 391438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770647 RingCT/type: yes/0
Extra: 016b1507e16e6f051831f33f680c096052a0771cfbaf2654903d1de8216a70ce9f021100000022d6e4826b000000000000000000

1 output(s) for total of 30.974462324000 dcy

stealth address amount amount idx
00: 09988c1d4eeea27182fec21c2e50f7b7b18e4dbde241f3c79fb0f250aec76791 30.974462324000 787839 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": 391448, "vin": [ { "gen": { "height": 391438 } } ], "vout": [ { "amount": 30974462324, "target": { "key": "09988c1d4eeea27182fec21c2e50f7b7b18e4dbde241f3c79fb0f250aec76791" } } ], "extra": [ 1, 107, 21, 7, 225, 110, 111, 5, 24, 49, 243, 63, 104, 12, 9, 96, 82, 160, 119, 28, 251, 175, 38, 84, 144, 61, 29, 232, 33, 106, 112, 206, 159, 2, 17, 0, 0, 0, 34, 214, 228, 130, 107, 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