Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477c9d8832eee5373a13301cbd246c4f09774b703ddb64f3d8a00ab352f21c09

Tx prefix hash: cafd420aab3d9f84bc17574e2bded13452a3c6efed758e9c3c37177eae0a2834
Tx public key: 4bf706453e4e0c6b092cb24c7a7c119579223645923f93d9fceb8327c3081fa4
Timestamp: 1723364464 Timestamp [UCT]: 2024-08-11 08:21:04 Age [y:d:h:m:s]: 00:073:10:58:34
Block: 1085454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52580 RingCT/type: yes/0
Extra: 014bf706453e4e0c6b092cb24c7a7c119579223645923f93d9fceb8327c3081fa4021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4865ddf45fccad3ad241b833c476a346f98e5e6eadd672dfc787b79bdbdd96d7 0.600000000000 1560037 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": 1085464, "vin": [ { "gen": { "height": 1085454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4865ddf45fccad3ad241b833c476a346f98e5e6eadd672dfc787b79bdbdd96d7" } } ], "extra": [ 1, 75, 247, 6, 69, 62, 78, 12, 107, 9, 44, 178, 76, 122, 124, 17, 149, 121, 34, 54, 69, 146, 63, 147, 217, 252, 235, 131, 39, 195, 8, 31, 164, 2, 17, 0, 0, 0, 9, 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