Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47c588819fe31ca71e6560b1b85d5a109e17bbdae3e1613c2190306b03e02f9

Tx prefix hash: 0ff2f6aa90bce7cee21c7a9c705d7a98c7d6dffa2580ec282aeef95bd7716137
Tx public key: d3651f3daec455843f1378c69bf2dfee83ee2f6f87ca6cee8a7393f7e7dbd8c6
Timestamp: 1722110119 Timestamp [UCT]: 2024-07-27 19:55:19 Age [y:d:h:m:s]: 00:301:23:07:30
Block: 1075050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215759 RingCT/type: yes/0
Extra: 01d3651f3daec455843f1378c69bf2dfee83ee2f6f87ca6cee8a7393f7e7dbd8c602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74994788800a37e3f642e8eac75dce5dfd44cb5f3988b631d047bb551abd482a 0.600000000000 1547571 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": 1075060, "vin": [ { "gen": { "height": 1075050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74994788800a37e3f642e8eac75dce5dfd44cb5f3988b631d047bb551abd482a" } } ], "extra": [ 1, 211, 101, 31, 61, 174, 196, 85, 132, 63, 19, 120, 198, 155, 242, 223, 238, 131, 238, 47, 111, 135, 202, 108, 238, 138, 115, 147, 247, 231, 219, 216, 198, 2, 17, 0, 0, 0, 6, 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