Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4baca8434dd1cc75c309c007d2099dca728529c2cc30da021523afa8d8853945

Tx prefix hash: f79b36e2ce739d280fb6efcad9fddcb5882c4daef681ff1df826f718bf0e97d2
Tx public key: 3a5c82b294c8abd60c4af2964d25332927d6fe936523893d85cc7d00e856af22
Timestamp: 1736025055 Timestamp [UCT]: 2025-01-04 21:10:55 Age [y:d:h:m:s]: 00:162:22:10:15
Block: 1190281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116162 RingCT/type: yes/0
Extra: 013a5c82b294c8abd60c4af2964d25332927d6fe936523893d85cc7d00e856af2202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6fa95b3f6c70ad7b4f09275e8909f7066c9fb1d99e0034bfa11ff50490d1867 0.600000000000 1676796 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": 1190291, "vin": [ { "gen": { "height": 1190281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6fa95b3f6c70ad7b4f09275e8909f7066c9fb1d99e0034bfa11ff50490d1867" } } ], "extra": [ 1, 58, 92, 130, 178, 148, 200, 171, 214, 12, 74, 242, 150, 77, 37, 51, 41, 39, 214, 254, 147, 101, 35, 137, 61, 133, 204, 125, 0, 232, 86, 175, 34, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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