Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d705f6c71b795ded6ff39eed134ffc822fb63dbb6e360b8bee86167fb49ea43

Tx prefix hash: 09d5fe36430dd64eff50fcd4000e60a903b5d754edf836464d2f35b7a3f351df
Tx public key: 3d273bbbddbb881eb48a33e2d07a0be9e940a6212124e6c021796d4d2aff2030
Timestamp: 1633067009 Timestamp [UCT]: 2021-10-01 05:43:29 Age [y:d:h:m:s]: 03:244:07:59:06
Block: 344265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951397 RingCT/type: yes/0
Extra: 013d273bbbddbb881eb48a33e2d07a0be9e940a6212124e6c021796d4d2aff203002110000000137cb3088000000000000000000

1 output(s) for total of 44.394032387000 dcy

stealth address amount amount idx
00: 3adaa27fe701117a4c35cd5f750a23b89298a9c58c6d20b62be359c30f906738 44.394032387000 706439 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": 344275, "vin": [ { "gen": { "height": 344265 } } ], "vout": [ { "amount": 44394032387, "target": { "key": "3adaa27fe701117a4c35cd5f750a23b89298a9c58c6d20b62be359c30f906738" } } ], "extra": [ 1, 61, 39, 59, 187, 221, 187, 136, 30, 180, 138, 51, 226, 208, 122, 11, 233, 233, 64, 166, 33, 33, 36, 230, 192, 33, 121, 109, 77, 42, 255, 32, 48, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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