Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46873ed4762c4e01c923991fff749cbb86c1a6d85a284625d461b683a971b34e

Tx prefix hash: e469dce597e6d205d5a823ccbb8f95bd18b3f5350a6eade3efbe9d8e82f596c3
Tx public key: 20775d67d29f95424194058af15069fc817ba242681fc7d8eb2fdc4076a2376a
Timestamp: 1727385317 Timestamp [UCT]: 2024-09-26 21:15:17 Age [y:d:h:m:s]: 01:042:18:36:25
Block: 1118783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288963 RingCT/type: yes/0
Extra: 0120775d67d29f95424194058af15069fc817ba242681fc7d8eb2fdc4076a2376a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21c7fca55cc70a67df5a7d67f05e8ac5ca1b75dd5b8a94da41053d8bdbf897d9 0.600000000000 1600096 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": 1118793, "vin": [ { "gen": { "height": 1118783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21c7fca55cc70a67df5a7d67f05e8ac5ca1b75dd5b8a94da41053d8bdbf897d9" } } ], "extra": [ 1, 32, 119, 93, 103, 210, 159, 149, 66, 65, 148, 5, 138, 241, 80, 105, 252, 129, 123, 162, 66, 104, 31, 199, 216, 235, 47, 220, 64, 118, 162, 55, 106, 2, 17, 0, 0, 0, 2, 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