Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495b56131a8274f3a8f34ed96672ef69c7ddf7dcbbf14c5f4aef8ed9fdb14416

Tx prefix hash: c3c5dea9fe082201ca1ef0e1adb1a0d77c23955e8320575428db88314d99f45e
Tx public key: 235f0e270f869f02c92e53b8efa362b96bcf28553d827f3aa68e5b9872987a56
Timestamp: 1724398311 Timestamp [UCT]: 2024-08-23 07:31:51 Age [y:d:h:m:s]: 01:100:09:07:09
Block: 1094036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330205 RingCT/type: yes/0
Extra: 01235f0e270f869f02c92e53b8efa362b96bcf28553d827f3aa68e5b9872987a5602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be62b6ba893e10e6507ada496a8b4879084a6c514c8c29891f9ef5a31ff9c28a 0.600000000000 1569097 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": 1094046, "vin": [ { "gen": { "height": 1094036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be62b6ba893e10e6507ada496a8b4879084a6c514c8c29891f9ef5a31ff9c28a" } } ], "extra": [ 1, 35, 95, 14, 39, 15, 134, 159, 2, 201, 46, 83, 184, 239, 163, 98, 185, 107, 207, 40, 85, 61, 130, 127, 58, 166, 142, 91, 152, 114, 152, 122, 86, 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