Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e489985bd7d131d439f421aa3983c10917e9d2945b80b2df8ad3a6e5d401a1d6

Tx prefix hash: 5d7107a1a0902557f108986052d0e63c3da1eb0dd9f0a2cb3ebf0a9f08fbebfd
Tx public key: f669059a7c6cbeb860774e2e979759b060148335b5e5545d5e44f05a0a5fd027
Timestamp: 1723584997 Timestamp [UCT]: 2024-08-13 21:36:37 Age [y:d:h:m:s]: 00:236:06:44:50
Block: 1087279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168737 RingCT/type: yes/0
Extra: 01f669059a7c6cbeb860774e2e979759b060148335b5e5545d5e44f05a0a5fd02702110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435b56dca8c3e4e6c421b03745f3df2723d9f4eb57747f66a90cac5c622e08fe 0.600000000000 1561886 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": 1087289, "vin": [ { "gen": { "height": 1087279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435b56dca8c3e4e6c421b03745f3df2723d9f4eb57747f66a90cac5c622e08fe" } } ], "extra": [ 1, 246, 105, 5, 154, 124, 108, 190, 184, 96, 119, 78, 46, 151, 151, 89, 176, 96, 20, 131, 53, 181, 229, 84, 93, 94, 68, 240, 90, 10, 95, 208, 39, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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