Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9828c9bb1853d5cb219fe0060ba9520b44aeec3a07bc22429acbe9b93146a0

Tx prefix hash: b53c533e28bae9bae6403d8c828b23b5fff72d1b1e71731b4ff899b9f56532b1
Tx public key: c9f827da18631d29e915d1d9dbdfe130d6bdde6c1a850d112c2e8f6aa76e1cf7
Timestamp: 1722334334 Timestamp [UCT]: 2024-07-30 10:12:14 Age [y:d:h:m:s]: 01:099:20:40:00
Block: 1076912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329847 RingCT/type: yes/0
Extra: 01c9f827da18631d29e915d1d9dbdfe130d6bdde6c1a850d112c2e8f6aa76e1cf7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f15b28150e580e56f975d5281824cda317f28c07eced2f89d08b5687a6e35631 0.600000000000 1549455 of 15

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": 1076922, "vin": [ { "gen": { "height": 1076912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f15b28150e580e56f975d5281824cda317f28c07eced2f89d08b5687a6e35631" } } ], "extra": [ 1, 201, 248, 39, 218, 24, 99, 29, 41, 233, 21, 209, 217, 219, 223, 225, 48, 214, 189, 222, 108, 26, 133, 13, 17, 44, 46, 143, 106, 167, 110, 28, 247, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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