Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb7149d2c4445bf0fae83dd329c22f19923f5e38c084705338d5dba2b9977d4

Tx prefix hash: c3198dd285ea85903dfd6ff7638986120613cc0636624a309d9e53b0ff6f78c1
Tx public key: b01be20fa86e707fbd18f3753c1425d7972f9ebea94c1cf74343a4ae43a037df
Timestamp: 1729022083 Timestamp [UCT]: 2024-10-15 19:54:43 Age [y:d:h:m:s]: 00:099:09:13:10
Block: 1132358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70988 RingCT/type: yes/0
Extra: 01b01be20fa86e707fbd18f3753c1425d7972f9ebea94c1cf74343a4ae43a037df021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74e4a8ed27452ad43f4f0d1006f9c453714061a49d2a33e319dcd3dcae6d9bba 0.600000000000 1615271 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": 1132368, "vin": [ { "gen": { "height": 1132358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74e4a8ed27452ad43f4f0d1006f9c453714061a49d2a33e319dcd3dcae6d9bba" } } ], "extra": [ 1, 176, 27, 226, 15, 168, 110, 112, 127, 189, 24, 243, 117, 60, 20, 37, 215, 151, 47, 158, 190, 169, 76, 28, 247, 67, 67, 164, 174, 67, 160, 55, 223, 2, 17, 0, 0, 0, 4, 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