Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e7b76d8c38390543b6a218e10e23dd2f998cc03acceacd0b45d466190eb8d83

Tx prefix hash: 248ad62ec5dee5b0d76c5203165c03a8cf1d52367a7a9f90b2120bdb09778e9b
Tx public key: 30c5fc9b98071fa9d71a2c2a17d9bd59d53d5abc254282fa91abf3f5e56735a2
Timestamp: 1649628251 Timestamp [UCT]: 2022-04-10 22:04:11 Age [y:d:h:m:s]: 02:260:22:49:17
Block: 477549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706282 RingCT/type: yes/0
Extra: 0130c5fc9b98071fa9d71a2c2a17d9bd59d53d5abc254282fa91abf3f5e56735a202110000000e4da16a3a000000000000000000

1 output(s) for total of 16.057656426000 dcy

stealth address amount amount idx
00: f050469d757de49cc3c89310ce19ed80da3dfa72e89eb790b297b9fe37c14477 16.057656426000 898220 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": 477559, "vin": [ { "gen": { "height": 477549 } } ], "vout": [ { "amount": 16057656426, "target": { "key": "f050469d757de49cc3c89310ce19ed80da3dfa72e89eb790b297b9fe37c14477" } } ], "extra": [ 1, 48, 197, 252, 155, 152, 7, 31, 169, 215, 26, 44, 42, 23, 217, 189, 89, 213, 61, 90, 188, 37, 66, 130, 250, 145, 171, 243, 245, 229, 103, 53, 162, 2, 17, 0, 0, 0, 14, 77, 161, 106, 58, 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