Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb05b5be96c7496cac91ff2994122eb4bccfa2cb94e6b356964479661032d5b3

Tx prefix hash: 29ba618bd853ae4bb5763d7076de5971fba8b44c287845992a94fefb5553c6b1
Tx public key: 33923b8f3fab06bb7006ad7eb0b69a28b7cf1f7e3c3526e40e1c751897347151
Timestamp: 1717513100 Timestamp [UCT]: 2024-06-04 14:58:20 Age [y:d:h:m:s]: 00:341:18:25:41
Block: 1036951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244263 RingCT/type: yes/0
Extra: 0133923b8f3fab06bb7006ad7eb0b69a28b7cf1f7e3c3526e40e1c7518973471510211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3933ab5a5cfd3e45a8ad3a8249d1d13eba02bdbc6b0355616d155dbb3319e11 0.600000000000 1505482 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": 1036961, "vin": [ { "gen": { "height": 1036951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3933ab5a5cfd3e45a8ad3a8249d1d13eba02bdbc6b0355616d155dbb3319e11" } } ], "extra": [ 1, 51, 146, 59, 143, 63, 171, 6, 187, 112, 6, 173, 126, 176, 182, 154, 40, 183, 207, 31, 126, 60, 53, 38, 228, 14, 28, 117, 24, 151, 52, 113, 81, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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