Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3da9de9b6b60c1e396cdd53c1cc155dd66aed4e969cd7a6fe0445bf442aaac4

Tx prefix hash: 855997a56ee984d1d5a506329f65a06ac262d1599e6e3dc1b0f51e044f891c20
Tx public key: f3e08e4ef00e8ac3548a19a88422e3163145aa54fd18cb96840586eecc72a2cd
Timestamp: 1696893116 Timestamp [UCT]: 2023-10-09 23:11:56 Age [y:d:h:m:s]: 01:140:08:45:53
Block: 866197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361317 RingCT/type: yes/0
Extra: 01f3e08e4ef00e8ac3548a19a88422e3163145aa54fd18cb96840586eecc72a2cd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.827808338000 dcy

stealth address amount amount idx
00: daf08ea8fd26bdee0e32a427df78df998ae552791d5d1b3d62a8143d23afa3fa 0.827808338000 1320775 of 0

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": 866207, "vin": [ { "gen": { "height": 866197 } } ], "vout": [ { "amount": 827808338, "target": { "key": "daf08ea8fd26bdee0e32a427df78df998ae552791d5d1b3d62a8143d23afa3fa" } } ], "extra": [ 1, 243, 224, 142, 78, 240, 14, 138, 195, 84, 138, 25, 168, 132, 34, 227, 22, 49, 69, 170, 84, 253, 24, 203, 150, 132, 5, 134, 238, 204, 114, 162, 205, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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