Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f63f2c6e58eebcf5a04f05511948ac35bd942003cf84b9c2589962dc1def118d

Tx prefix hash: 427a6f9c3c3a49f8d85e04c530e4687ffb502e83780a23075fa99efb6515350a
Tx public key: 8a95f3be0679f5784f05bf0f2e8da8f5b94f060d544235ebe321dd75c1bc1f4b
Timestamp: 1717387890 Timestamp [UCT]: 2024-06-03 04:11:30 Age [y:d:h:m:s]: 00:304:16:17:53
Block: 1035907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217733 RingCT/type: yes/0
Extra: 018a95f3be0679f5784f05bf0f2e8da8f5b94f060d544235ebe321dd75c1bc1f4b0211000000054385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d04a5f89a7c4431c6b2b67bf30ea91edd09def72f1e0396ecbf07cffbba751 0.600000000000 1504432 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": 1035917, "vin": [ { "gen": { "height": 1035907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d04a5f89a7c4431c6b2b67bf30ea91edd09def72f1e0396ecbf07cffbba751" } } ], "extra": [ 1, 138, 149, 243, 190, 6, 121, 245, 120, 79, 5, 191, 15, 46, 141, 168, 245, 185, 79, 6, 13, 84, 66, 53, 235, 227, 33, 221, 117, 193, 188, 31, 75, 2, 17, 0, 0, 0, 5, 67, 133, 54, 42, 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