Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4ccc281240b800ac2939599c6e16e58e48f8e7b8bbb5e4276ed4809b8d1bee0

Tx prefix hash: f0456f20380add0065d6fb5d8838c68efa320eaed32b4ad5bacc4787dedc2bcd
Tx public key: e9177fa7d0a310364fc8af2004760b84796d35d6e790b251d754d973941c8190
Timestamp: 1695388962 Timestamp [UCT]: 2023-09-22 13:22:42 Age [y:d:h:m:s]: 02:109:17:41:23
Block: 853716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598164 RingCT/type: yes/0
Extra: 01e9177fa7d0a310364fc8af2004760b84796d35d6e790b251d754d973941c81900211000000054b8f5122000000000000000000

1 output(s) for total of 0.910509641000 dcy

stealth address amount amount idx
00: 2bfa485b5dd0bf10c33be50c550d0393ce812c13510bf4fd219fb3152f843e8f 0.910509641000 1307646 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": 853726, "vin": [ { "gen": { "height": 853716 } } ], "vout": [ { "amount": 910509641, "target": { "key": "2bfa485b5dd0bf10c33be50c550d0393ce812c13510bf4fd219fb3152f843e8f" } } ], "extra": [ 1, 233, 23, 127, 167, 208, 163, 16, 54, 79, 200, 175, 32, 4, 118, 11, 132, 121, 109, 53, 214, 231, 144, 178, 81, 215, 84, 217, 115, 148, 28, 129, 144, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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