Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28b43a891bbc96dac48a73efcc5e4fe9b81387d3507e6d679be3cb3809563567

Tx prefix hash: 4a52f2ec38e8cbb9f5321f0eb5a8df9c85c283303f7081b8a4df70203a1c5372
Tx public key: f1eda92d5459ae1f078085472ef027732613ca8174e5de3bf784a6f0465ab9e8
Timestamp: 1724159050 Timestamp [UCT]: 2024-08-20 13:04:10 Age [y:d:h:m:s]: 00:226:13:08:32
Block: 1092035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161773 RingCT/type: yes/0
Extra: 01f1eda92d5459ae1f078085472ef027732613ca8174e5de3bf784a6f0465ab9e802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d4fabb9736cf42caee785ee8b9fbb4ab801dd69f8d98c0cc9daec21bbb4296 0.600000000000 1566694 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": 1092045, "vin": [ { "gen": { "height": 1092035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d4fabb9736cf42caee785ee8b9fbb4ab801dd69f8d98c0cc9daec21bbb4296" } } ], "extra": [ 1, 241, 237, 169, 45, 84, 89, 174, 31, 7, 128, 133, 71, 46, 240, 39, 115, 38, 19, 202, 129, 116, 229, 222, 59, 247, 132, 166, 240, 70, 90, 185, 232, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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