Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff2ae93d70fee4a954f8cee5c2202e6dd32750fb6445c55e88c4bb948f1cac9

Tx prefix hash: 990ae5f9829c3ffcd7124242d9bd4f5acf3f35f7e0c616a14b08215b16f400ca
Tx public key: 473b654694e17ac711632ef2d10ed925d207d15793b5c093c06802442523ad62
Timestamp: 1739726001 Timestamp [UCT]: 2025-02-16 17:13:21 Age [y:d:h:m:s]: 00:024:00:14:28
Block: 1220620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17215 RingCT/type: yes/0
Extra: 01473b654694e17ac711632ef2d10ed925d207d15793b5c093c06802442523ad62021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da1beee72ab0b8564f0737994d96561abdef5dcb0055019139144e1f2ac8386 0.600000000000 1707461 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": 1220630, "vin": [ { "gen": { "height": 1220620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da1beee72ab0b8564f0737994d96561abdef5dcb0055019139144e1f2ac8386" } } ], "extra": [ 1, 71, 59, 101, 70, 148, 225, 122, 199, 17, 99, 46, 242, 209, 14, 217, 37, 210, 7, 209, 87, 147, 181, 192, 147, 192, 104, 2, 68, 37, 35, 173, 98, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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