Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26bf1f78522fd8aa0adec8c5d9fdbe35dcc9bfbcc4e639d212aba27dfbd564a8

Tx prefix hash: 3bb434fd3644ba042a5703e727379fe7af43e66e8b3b1b1612c353630194b1ed
Tx public key: 425d15d83d1f7fdf75350dd47896d7356c3cac303d6b226a147049d9d3ecd1ef
Timestamp: 1734047151 Timestamp [UCT]: 2024-12-12 23:45:51 Age [y:d:h:m:s]: 00:103:16:53:24
Block: 1173923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73873 RingCT/type: yes/0
Extra: 01425d15d83d1f7fdf75350dd47896d7356c3cac303d6b226a147049d9d3ecd1ef0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50805d43c9c6d510637bc465fbae8fa8bc7f2db8c52bea2d058f09ff3c92c16a 0.600000000000 1660012 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": 1173933, "vin": [ { "gen": { "height": 1173923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50805d43c9c6d510637bc465fbae8fa8bc7f2db8c52bea2d058f09ff3c92c16a" } } ], "extra": [ 1, 66, 93, 21, 216, 61, 31, 127, 223, 117, 53, 13, 212, 120, 150, 215, 53, 108, 60, 172, 48, 61, 107, 34, 106, 20, 112, 73, 217, 211, 236, 209, 239, 2, 17, 0, 0, 0, 6, 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