Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ed5778b46805094f7792fc3bfd1d891c90bd4e7fb5421477e538b1513e140f

Tx prefix hash: 79bbcf1e9d53201dccf0f009f7406db385dfc271652c9f8944848184b401ca7c
Tx public key: 8ba6233847488f6f217e12cfd7335a4255f0a8d4536a9f41e54021d1ad6b51f9
Timestamp: 1704696494 Timestamp [UCT]: 2024-01-08 06:48:14 Age [y:d:h:m:s]: 01:332:06:34:34
Block: 930659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496353 RingCT/type: yes/0
Extra: 018ba6233847488f6f217e12cfd7335a4255f0a8d4536a9f41e54021d1ad6b51f90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 124850d4086b02aa805ef57ba12e9f8256ed5b20ae95ed7a1143ce1a5f5013b9 0.600000000000 1388545 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": 930669, "vin": [ { "gen": { "height": 930659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "124850d4086b02aa805ef57ba12e9f8256ed5b20ae95ed7a1143ce1a5f5013b9" } } ], "extra": [ 1, 139, 166, 35, 56, 71, 72, 143, 111, 33, 126, 18, 207, 215, 51, 90, 66, 85, 240, 168, 212, 83, 106, 159, 65, 229, 64, 33, 209, 173, 107, 81, 249, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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