Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54cebdbf9036da114ffb521e372bb38bbc4195fdeb1bace45ea34dd5a23333f3

Tx prefix hash: 39b02a98f65901e3a7fdb78fb95a42c8c5761be1fbb03f1b173ae8dd316d90ad
Tx public key: f540b57af82bc8aeb9169f39f3005dac3c295cf375a052fcae0294a055bcb9cb
Timestamp: 1634779841 Timestamp [UCT]: 2021-10-21 01:30:41 Age [y:d:h:m:s]: 03:216:22:51:03
Block: 357118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 933134 RingCT/type: yes/0
Extra: 01f540b57af82bc8aeb9169f39f3005dac3c295cf375a052fcae0294a055bcb9cb021100000002573e6fef000000000000000000

1 output(s) for total of 40.245769213000 dcy

stealth address amount amount idx
00: b421f88b34b2ad67c3c045d65abbe6a2ebec267c4f0d4ce4877c3b2a6af1f943 40.245769213000 728334 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": 357128, "vin": [ { "gen": { "height": 357118 } } ], "vout": [ { "amount": 40245769213, "target": { "key": "b421f88b34b2ad67c3c045d65abbe6a2ebec267c4f0d4ce4877c3b2a6af1f943" } } ], "extra": [ 1, 245, 64, 181, 122, 248, 43, 200, 174, 185, 22, 159, 57, 243, 0, 93, 172, 60, 41, 92, 243, 117, 160, 82, 252, 174, 2, 148, 160, 85, 188, 185, 203, 2, 17, 0, 0, 0, 2, 87, 62, 111, 239, 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