Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d0462fddf0c0fa5fb8dc09f17c975f216e4b617cbedd0a6b42779ec811be02f

Tx prefix hash: 7934e23670163776b043a2ff1ac79e2d925b742a8b8fed6407818543c34d2b3e
Tx public key: 612f53828c332adcbfc5d35257bca4f59f0643f298f4d34147a9a908c39d2468
Timestamp: 1734485372 Timestamp [UCT]: 2024-12-18 01:29:32 Age [y:d:h:m:s]: 00:325:16:07:17
Block: 1177562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230235 RingCT/type: yes/0
Extra: 01612f53828c332adcbfc5d35257bca4f59f0643f298f4d34147a9a908c39d24680211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac7ef919eb8ada732f1281486b2f74fd582895328c586be7acb4e9dfde6682cf 0.600000000000 1663933 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": 1177572, "vin": [ { "gen": { "height": 1177562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac7ef919eb8ada732f1281486b2f74fd582895328c586be7acb4e9dfde6682cf" } } ], "extra": [ 1, 97, 47, 83, 130, 140, 51, 42, 220, 191, 197, 211, 82, 87, 188, 164, 245, 159, 6, 67, 242, 152, 244, 211, 65, 71, 169, 169, 8, 195, 157, 36, 104, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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