Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a55dc207f52c15ddb7bb6208e67abbbb193ce7dbfebecc5edb72a36bb28d02

Tx prefix hash: 27ca3f325460e1fba07d3c5cec918d6f6273b5aa3d13e150621381b3049d3583
Tx public key: 0c11c7208b8b3e998ce53455d0f3f6d06722c408d83db2a66353942273cee46b
Timestamp: 1723391229 Timestamp [UCT]: 2024-08-11 15:47:09 Age [y:d:h:m:s]: 00:282:18:08:47
Block: 1085669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202008 RingCT/type: yes/0
Extra: 010c11c7208b8b3e998ce53455d0f3f6d06722c408d83db2a66353942273cee46b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e63f6943c9abca50a4313b4ab94d00a189b95df874f83f0e6d291052ce43dbab 0.600000000000 1560258 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": 1085679, "vin": [ { "gen": { "height": 1085669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e63f6943c9abca50a4313b4ab94d00a189b95df874f83f0e6d291052ce43dbab" } } ], "extra": [ 1, 12, 17, 199, 32, 139, 139, 62, 153, 140, 229, 52, 85, 208, 243, 246, 208, 103, 34, 196, 8, 216, 61, 178, 166, 99, 83, 148, 34, 115, 206, 228, 107, 2, 17, 0, 0, 0, 1, 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