Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9db3aec1a1f52afe9b27333c6f11dfc80990c8fa37ffcfd57db4a5b28417613

Tx prefix hash: 1890b5303ee43b6a575c3dafc7d3513c821b7f62ee3f8dd6ae95ea3f2f15e5ae
Tx public key: 289a4914c716ebb3cdd4e34ca4c5f814ae404209e6b7df211954a691d1dc6b29
Timestamp: 1580351080 Timestamp [UCT]: 2020-01-30 02:24:40 Age [y:d:h:m:s]: 05:035:02:41:55
Block: 54916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176808 RingCT/type: yes/0
Extra: 01289a4914c716ebb3cdd4e34ca4c5f814ae404209e6b7df211954a691d1dc6b290211000000084943cd9f000000000000000000

1 output(s) for total of 403.683799743000 dcy

stealth address amount amount idx
00: ec2341e8b68018e56f76e137b5606c9c5628be133abdf8927655e75499314f93 403.683799743000 101556 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": 54926, "vin": [ { "gen": { "height": 54916 } } ], "vout": [ { "amount": 403683799743, "target": { "key": "ec2341e8b68018e56f76e137b5606c9c5628be133abdf8927655e75499314f93" } } ], "extra": [ 1, 40, 154, 73, 20, 199, 22, 235, 179, 205, 212, 227, 76, 164, 197, 248, 20, 174, 64, 66, 9, 230, 183, 223, 33, 25, 84, 166, 145, 209, 220, 107, 41, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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