Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e4125890c825760a2b41d99113baedba1fc5a2a6f61bd1b6b15427772d4966

Tx prefix hash: 827da698d2d16c5813b6500a409a4f5044872f753c115502c4a7e1d52d00c100
Tx public key: 61a2ac33b6056552ef2353e9266d79f75e0f2024fe8776c57fab15f061de4608
Timestamp: 1732819820 Timestamp [UCT]: 2024-11-28 18:50:20 Age [y:d:h:m:s]: 00:123:13:04:26
Block: 1163740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88104 RingCT/type: yes/0
Extra: 0161a2ac33b6056552ef2353e9266d79f75e0f2024fe8776c57fab15f061de460802110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a5fdb5cd2fe56e6c6b9d4ae96bfd808e24a8fa7addc4bcc197493a71c26e6f9 0.600000000000 1649409 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": 1163750, "vin": [ { "gen": { "height": 1163740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a5fdb5cd2fe56e6c6b9d4ae96bfd808e24a8fa7addc4bcc197493a71c26e6f9" } } ], "extra": [ 1, 97, 162, 172, 51, 182, 5, 101, 82, 239, 35, 83, 233, 38, 109, 121, 247, 94, 15, 32, 36, 254, 135, 118, 197, 127, 171, 21, 240, 97, 222, 70, 8, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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