Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baaea92d9007c8db9f278175758b500becdb805b90c2e3063fe7c9cda9712c12

Tx prefix hash: a34662e8885e1b5e7b246ae11c6fd8486aef9cb820c049f8146604d6970f0165
Tx public key: 0cefaf4d1baa5930b62da11a21bf7a202d90a691d2214658c4a7a6ade687429c
Timestamp: 1715261334 Timestamp [UCT]: 2024-05-09 13:28:54 Age [y:d:h:m:s]: 00:193:20:19:51
Block: 1018279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138750 RingCT/type: yes/0
Extra: 010cefaf4d1baa5930b62da11a21bf7a202d90a691d2214658c4a7a6ade687429c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bfa3fbb60d486cb0908ada5139c7e4355b7284ff79cf7b176856e5df6fa4892 0.600000000000 1482068 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": 1018289, "vin": [ { "gen": { "height": 1018279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bfa3fbb60d486cb0908ada5139c7e4355b7284ff79cf7b176856e5df6fa4892" } } ], "extra": [ 1, 12, 239, 175, 77, 27, 170, 89, 48, 182, 45, 161, 26, 33, 191, 122, 32, 45, 144, 166, 145, 210, 33, 70, 88, 196, 167, 166, 173, 230, 135, 66, 156, 2, 17, 0, 0, 0, 1, 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