Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c62475ce819ce991e49b61190a41f9938edb453c99ea03b93ef55feae102611

Tx prefix hash: 60cffcb2de24bbf4629e1a5b858eb7d2d41c7176ba3eec4dfb102866a125f67d
Tx public key: 0ed61ff81d72556fe62a5008bedef8a6d5fd89a53ee3e07b39068affcd77e24d
Timestamp: 1613408393 Timestamp [UCT]: 2021-02-15 16:59:53 Age [y:d:h:m:s]: 03:311:15:05:18
Block: 199500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 981838 RingCT/type: yes/0
Extra: 010ed61ff81d72556fe62a5008bedef8a6d5fd89a53ee3e07b39068affcd77e24d021100000042a45716b1000000000000000000

1 output(s) for total of 133.961323556000 dcy

stealth address amount amount idx
00: 3c27c4ea6a2a3cdef8f0fa5beaa70cbccdc28ca4527de43cba20b36f88fd8bd9 133.961323556000 408240 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": 199510, "vin": [ { "gen": { "height": 199500 } } ], "vout": [ { "amount": 133961323556, "target": { "key": "3c27c4ea6a2a3cdef8f0fa5beaa70cbccdc28ca4527de43cba20b36f88fd8bd9" } } ], "extra": [ 1, 14, 214, 31, 248, 29, 114, 85, 111, 230, 42, 80, 8, 190, 222, 248, 166, 213, 253, 137, 165, 62, 227, 224, 123, 57, 6, 138, 255, 205, 119, 226, 77, 2, 17, 0, 0, 0, 66, 164, 87, 22, 177, 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