Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a311e9030f4d8364b7f4c8b016eb507e0d4ccffd25d153808e58cdb3b916d575

Tx prefix hash: c206572c56e7f131f5eab07b3bf61e46b7daa88b405821649898c9d992d7e49f
Tx public key: e3dc9e12bedad5bdff1a34d16beacd04d155eecb6ac5ec5ad1f2793d1e780160
Timestamp: 1702833599 Timestamp [UCT]: 2023-12-17 17:19:59 Age [y:d:h:m:s]: 01:033:11:28:55
Block: 915241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285238 RingCT/type: yes/0
Extra: 01e3dc9e12bedad5bdff1a34d16beacd04d155eecb6ac5ec5ad1f2793d1e78016002110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aef32c22f28c35dc306ab750bf23ab3c0726f0522894b859f4f4a4639820445 0.600000000000 1372631 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": 915251, "vin": [ { "gen": { "height": 915241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aef32c22f28c35dc306ab750bf23ab3c0726f0522894b859f4f4a4639820445" } } ], "extra": [ 1, 227, 220, 158, 18, 190, 218, 213, 189, 255, 26, 52, 209, 107, 234, 205, 4, 209, 85, 238, 203, 106, 197, 236, 90, 209, 242, 121, 61, 30, 120, 1, 96, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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