Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b784e9b8612af52eabbb7ffce6f8d960759798b6eef16d922d8df847a27f7c7

Tx prefix hash: 4bffaa68bf770fbeb346428a15d137ab7d5e525983e9a985bad057aa7385541a
Tx public key: 6a6a7e3228258625218a67ea41703f25cb7dbbd3f686a426a12987b9b6613466
Timestamp: 1746503438 Timestamp [UCT]: 2025-05-06 03:50:38 Age [y:d:h:m:s]: 00:156:08:57:09
Block: 1276749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109420 RingCT/type: yes/0
Extra: 016a6a7e3228258625218a67ea41703f25cb7dbbd3f686a426a12987b9b66134660211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699b70694dc6340d340d5daaa51569f8e9790ffa53fd4d0203f1a65fb8769965 0.600000000000 1764096 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": 1276759, "vin": [ { "gen": { "height": 1276749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699b70694dc6340d340d5daaa51569f8e9790ffa53fd4d0203f1a65fb8769965" } } ], "extra": [ 1, 106, 106, 126, 50, 40, 37, 134, 37, 33, 138, 103, 234, 65, 112, 63, 37, 203, 125, 187, 211, 246, 134, 164, 38, 161, 41, 135, 185, 182, 97, 52, 102, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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